<HTML>
<HEAD>
<TITLE> TOXFR User's Guide </TITLE>
</HEAD>

<BODY style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">

<A NAME="top"></A>

<TABLE STYLE="text-align: left; margin-left: auto; margin-right: auto; width: 800px;" BORDER="0" CELLPADDING="5" CELLSPACING="2">
<TBODY>
<TR>
  <TD STYLE="background-color: rgb(153, 153, 153); vertical-align: middle; text-align: center;">
  <DIV ALIGN="right">
    <SMALL><SMALL><A HREF="index.html">Index Page</A></SMALL></SMALL>
  </DIV>
  <B>TOXFR User's Guide</B> </TD>
</TR>
<TR>
  <TD STYLE="vertical-align: top;">

<H2> Table of Contents
</H2>

<PRE>
   <A HREF="#TOXFR User's Guide">TOXFR User's Guide</A>
      <A HREF="#Abstract">Abstract</A>
      <A HREF="#Summary">Summary</A>
      <A HREF="#Particulars">Particulars</A>
         <A HREF="#Examples">Examples</A>
      <A HREF="#Note about DAF Run-Time Binary File Format Translation">Note about DAF Run-Time Binary File Format Translation</A>

</PRE>

<HR SIZE=3 NOSHADE>

<BR><BR>
<A NAME="TOXFR User's Guide"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H1> TOXFR User's Guide
</H1><HR SIZE=3 NOSHADE><P><BR><BR><BR>
   Last revised on 2004 DEC 06 by B. V. Semenov.
<P>
 
<BR><BR>
<A NAME="Abstract"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H2> Abstract
</H2><HR ALIGN="LEFT" WIDTH=50% ><P><BR><BR>
   TOXFR is a command-line program that converts binary format SPK, CK and
   EK files to transfer format.
<P>
 
<BR><BR>
<A NAME="Summary"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H2> Summary
</H2><HR ALIGN="LEFT" WIDTH=50% ><P><BR><BR>
   TOXFR is a utility program providing command line, or ``batch,''
   oriented method for converting SPICE binary kernel files into portable
   transfer files. The name ``toxfr'' is, possibly not so obviously,
   derived from ``to transfer,'' as in ``convert to transfer.''
<P>
 
<BR><BR>
<A NAME="Particulars"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H2> Particulars
</H2><HR ALIGN="LEFT" WIDTH=50% ><P><BR><BR>
   TOXFR converts a SPICE binary kernel file into a transfer file format
   that is used to transfer, or port, the binary data to a different
   computing environment. TOXFR requires at least the name of the input
   binary file, which is the first argument on the command line.
   Optionally, a name for the output transfer file may be specified as the
   second argument on the command line. If a name for the output file is
   provided on the command line it overrides the automatic naming
   conventions used by the program.
<P>
 
   If only the name of the input binary file is provided on the command
   line, TOXFR will generate a name for the output transfer file that has
   the same base name as the input binary file and an appropriate filename
   extension, based on the filename extension of the binary file. If TOXFR
   does not recognize the filename extension of the input binary file, or
   there is no filename extension on the input binary file, a filename
   extension of '.xfr' will be used as the filename extension of the output
   transfer file. If a file having the same name as the output file already
   exists, TOXFR signals an error and stops. Again, we assume that it is
   bad form to overwrite or replace an existing file.
<P>
 
   TOXFR recognizes the filename extensions ``.bc'', ``.bee'', ``.bpc'',
   and ``.bsp'' which are associated with SPICE binary kernel files. These
   are converted to the transfer filename extensions ``.xc'', ``.xee'',
   ``.xpc'', and ``.xsp,'' respectively.
<P>
 
<BR><BR>
<A NAME="Examples"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H3> Examples
</H3><P><BR><BR>
   TOXFR requires the name of the file to be converted and, optionally, the
   name of the file to be produced, e.g.,
<P>
 
<PRE>
   prompt &gt; toxfr thisfile.bsp
</PRE>
   and
<P>
 
<PRE>
   prompt &gt; toxfr thisfile.bsp thisfile.xsp
</PRE>
   would both produce the file `thisfile.xsp' in the current directory.
<P>
 
   In the first example, the name for the transfer file produced is derived
   from the name of the binary file, using the full base name and replacing
   the letter `b' in the file name extension with the letter `x', to
   indicate that the file is a transfer file. In the second example, the
   name for the transfer file produced is taken directly from the command
   line.
<P>
 
<UL>
<TT>--</TT> Example 1: Convert the binary kernel file 'ephem.bsp' into a transfer file.
<BR><BR></UL>
<PRE>
            &gt; toxfr ephem.bsp
</PRE>
<UL>
<TT>&#32;&#32;</TT> This will create the transfer file 'ephem.xsp'.
<BR><BR></UL>
<UL>
<TT>--</TT> Example 2: This is the same as Example 1, except we explicitly set the
output filename on the command line.
<BR><BR></UL>
<PRE>
            &gt; toxfr ephem.bsp myephem.xsp
</PRE>
<UL>
<TT>&#32;&#32;</TT> This will create the transfer file 'myephem.xsp'.
<BR><BR></UL>
<UL>
<TT>--</TT> Example 3: For this example, we provide a filename extension on the input
binary file that TOXFR does not recognize.
<BR><BR></UL>
<PRE>
            &gt; toxfr mydata.bbb
</PRE>
<UL>
<TT>&#32;&#32;</TT> This will create the transfer file 'mydata.xfr'.
<BR><BR></UL>
<BR><BR>
<A NAME="Note about DAF Run-Time Binary File Format Translation"></A>
<p align="right"><a href="#top"><small>Top</small></a></p>
<H2> Note about DAF Run-Time Binary File Format Translation
</H2><HR ALIGN="LEFT" WIDTH=50% ><P><BR><BR>
   Starting with the N0052 release of the SPICE Toolkit (January, 2002)
   certain supported platforms are able to read DAF-based binary files
   (SPK, CK and binary PCK) that were written using a different, or
   non-native, binary representation. This capability eliminated the need
   to use transfer format to move DAF-based files between some of the
   platforms. Refer to the Convert User's Guide (<a href="../ug/convert.html">convert.ug</a>) to see if
   using transfer format files is indeed necessary in your data exchange
   path.
<P>
 

</TD>
</TR>
</TBODY>
</TABLE>

</BODY>

</HTML>
